Expand description
§vsdb_core
The core implementations of vsdb.
§Design Principles
Based on the underlying one-dimensional linear storage structure (native kv-database, such as rocksdb, etc.), multiple different namespaces are divided, and then abstract each dimension in the multi-dimensional logical structure based on these divided namespaces.
In the category of kv-database, namespaces can be expressed as different key ranges, or different key prefix.
This is the same as expressing complex data structures in computer memory(the memory itself is just a one-dimensional linear structure).
User data will be divided into two dimensions: ‘branch’ and ‘version’, the functions of the ‘basic’ category are stateless, and the functions of the ‘versioned’ category are stateful. In the internal implementation, each stateful function is implemented based on its corresponding stateless function, all stateful data has two additional identification dimensions (‘branch’ and ‘version’), somewhat like the logic in Git. Stateless functions do not have the feature of ‘version’ management, but they have higher performance.
§LICENSE
Re-exports§
pub use basic::mapx_raw::MapxRaw;
pub use common::vsdb_flush;
pub use common::vsdb_get_base_dir;
pub use common::vsdb_get_custom_dir;
pub use common::vsdb_set_base_dir;
pub use common::RawBytes;
pub use common::RawKey;
pub use common::RawValue;
pub use common::GB;
pub use common::KB;
pub use common::MB;
pub use common::NULL;
Modules§
- Unversioned functions.
- Common components
Macros§
- Parse bytes to a specified integer type.
- Parse bytes to a
Pre
type.